Skip to content

Conversation

electrum
Copy link
Member

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.

@wendigo
Copy link
Contributor

wendigo commented Jul 22, 2025

Test failure is related:

tests               | 2025-07-23 01:00:20 INFO: ManageTestResources.onFinish: running checks
tests               | FATAL: io.trino.testng.services.ManageTestResources: 
tests               | 	Test instance field has value that looks like a resource
tests               | 	    Test class: class io.trino.tests.product.deltalake.TestDeltaLakeActiveFilesCache
tests               | 	    Instance: io.trino.tests.product.deltalake.TestDeltaLakeActiveFilesCache@4f2d995e
tests               | 	    Field: private software.amazon.awssdk.services.s3.S3Client io.trino.tests.product.deltalake.TestDeltaLakeActiveFilesCache.s3
tests               | 	    Value: software.amazon.awssdk.services.s3.DefaultS3Client@2919aff3
tests               | 	    Test execution stage: AFTER_CLASS
tests               | 	    Matching rule: isAutoCloseable
tests               | 
tests               | 	Resources must not be allocated in a field initializer or a test constructor,
tests               | 	and must be freed when test class is completed.
tests               | 	Depending which rule has been violated, if the reported class holds on
tests               | 	to resources only conditionally, you can add @ResourcePresence to declare that.
tests               | 
tests               | JVM will be terminated
tests               | (exited)
tests               | (exited)

@wendigo
Copy link
Contributor

wendigo commented Jul 23, 2025

I've fixed remaining issues in the delta-lake tests (unclosed s3 instances)

@electrum
Copy link
Member Author

Thanks. Do you know why we didn't have this problem before?

@electrum electrum merged commit 8209002 into trinodb:master Jul 23, 2025
41 checks passed
@github-actions github-actions bot added this to the 477 milestone Jul 23, 2025
@wendigo
Copy link
Contributor

wendigo commented Jul 23, 2025

@electrum I guess because previous client wasn't a Closeable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants